Add Databricks plugin for Unity Catalog + SQL Warehouse compute #236
Conversation
| {%- set external = source_node.external -%} | ||
| {%- set partitions = external.partitions -%} | ||
| {%- set options = external.options -%} | ||
|
|
There was a problem hiding this comment.
Love that you've created this PR. Been thinking about doing it myself for a while, but haven't gotten further than overriding the databricks__create_external_table and databricks__get_external_build_plan macros locally.
One idea you could take into account is adding the support for liquid clustering:
|
Love to use this one! Any chance this one is going to main? |
|
@FlorianSchroevers @CodeGeek1212 @grindheim have y'all been using these macros already by chance by adding to your dbt project's I haven't yet had the chance to test them or this PR, but would like to understand how "ready for primetime" they are. Because setting up the CI infrastructure is a non-trivial amount of work in and of itself |
Description & motivation
resolves: #269
This change adds a Databricks plugin that can be used for Databricks using SQL Warehouse compute with Unity Catalog enabled, which is not possible using the spark plugin. I have used this fork of the repository successfully within my organization for several months now. It also moves the
alter table ... recover partitionsdefinition from the spark plugin to common, since it's named 'default'.Differences between databricks plugin and spark plugin:
old_relationvariable in get_external_build_plan, since Unity Catalog provides another layer in the hierarchy (catalogs).I'd be happy to make changes to my fork if necessary.
Checklist